set plugin development find-links only on the needed resolve#23024
set plugin development find-links only on the needed resolve#23024cburroughs merged 1 commit intopantsbuild:mainfrom
Conversation
|
(Back to draft, found a complication.) |
|
Thanks for the contribution. We've just branched for 2.31.x, so merging this pull request now will come out in 2.32.x, please move the release notes updates to docs/notes/2.32.x.md if that's appropriate. |
As described at <pantsbuild#21223 (comment)>, if you set find-links (and that includes everyone with in-repo plugins by way of `pants.backend.plugin_development`) on one resolve, we were erroneously setting it for *all* resolves during lockfile generation. This materially impacts resolution time.
9c0bbba to
0ad731d
Compare
The code was correct, but my description/changelog was wrong and mislead me when I looked at it later. This change fixes the narrow issue of |
@tobni yes. Exactly all indexes in use in a resolve must support PEP-658 if you want to get faster resolves (due to lack of wheel downloads to learn metadata). |
As described at
#21223 (comment), if you set find-links (and that includes everyone with in-repo plugins by way of
pants.backend.plugin_development) on one resolve, we were erroneously setting it for all resolves during lockfile generation. This materially impacts resolution time.